The Enterprise Operations EIE is the workhorse Equipment Interface Engine of the Enterprise Objects component of the CygNet Enterprise Integration Suite. This EIE processes properly formatted XML request and response files and provides the interface which allows data sharing between CygNet SCADA and a variety of other enterprise applications.
A 64-bit version of this EIE is available. See 64-bit Device Drivers.
An Enterprise Operations device monitors a file system directory that has been identified as its “inbox.” When an XML document representing a “request” is placed in the folder, the device immediately begins processing the request and produces an XML document that is the “response.”
The XML format for the request and response documents is specified in an XML Schema Definition (XSD) file. The Enterprise Operations schema language (XSD) is compiled into the Enterprise Operations EIE.
Only one operation per request file is allowed.
The Enterprise Operations EIE uses the Microsoft file system as the repository for request and response files. As files are processed by the system, they are moved to the applicable directory.
| Directory | Description |
|---|---|
|
Input Requests |
The directory in which the Enterprise Operations EIE checks for Input Request Files. |
|
In-Progress Requests |
The directory in which a Request File is stored while it is in-progress. The first step in processing a request is to move the Request File to the In Progress Requests folder. The file remains in this folder during processing, or if processing fails. |
|
Output Responses |
The directory in which the Output Response Files are stored. An output file is the result of a Request File. |
|
Processed Requests |
The directory in which processed Request Files are stored once processing is complete. |
File names are required to be unique within the system. If request files arrive in the system and another file with the same name is already found in the directory, at any processing stage, this results in a File Name Collision. Options for file collision action can be chosen during device configuration.
More:
|
|
|
